Zadig 文档
Zadig
教程
博客
论坛
关于
中文英文
Zadig
教程
博客
论坛
关于
Zadig v4.0
Loading...
     编辑文档
     反馈问题
     社区讨论

    本页导航

    v1.10.0 Release Notes

    Zadig v1.10.0 was released on March 8, 2022.

    # Feature List

    System

    • Redesigned interface to improve user experience

    Project

    • Support custom collaboration mode
    • Helm type projects support synchronizing services from Gerrit code source/Chart repository

    Workflow

    • Workflow tasks/test tasks running steps display detailed status information
    • Workflow/test build cache strategy optimization
    • Workflow build/test build support Serverless K8s clusters
    • Workflow supports configuring extension steps to integrate with external systems

    Environment

    • Service list loading efficiency optimization
    • Support creating environments based on existing namespaces

    System Settings

    • System configuration supports setting system task concurrency
    • Code source integration supports enabling proxy for individual code sources

    # Version Upgrade Process

    Warning

    If current system version < v1.9.0, please first upgrade to v1.9.0. For specific upgrade process, see v1.9.0 Upgrade Method, then follow the method below to upgrade to v1.10.0

    # Database Backup

    If already in production use, be sure to backup the database before upgrading

    1. Database backup commands:
    • Backup MongoDB data
    mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH
    
    1
    • Backup MySQL data
    mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
    mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql
    
    1
    2
    1. Database restore commands:
    • Restore MongoDB data
    mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH
    
    1
    • Restore MySQL data
    # Execute the following in MySQL:
    mysql> drop database user;
    mysql> create database user;
    mysql> drop database dex;
    mysql> create database dex;
    # Execute the following data recovery operations from command line:
    mysql -h <HOST> -P <PORT> -u root -p user < user.sql
    mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql
    
    1
    2
    3
    4
    5
    6
    7
    8

    # Upgrade Operations

    Please execute corresponding upgrade steps according to different installation methods.

    # Installation Method: All in One Installation Mode or Installation on Existing Kubernetes

    For both installation methods, use scripts from Installation on Existing KubernetesNew for upgrade.

    # Installation Method: Helm Command Installation

    For this installation method, execute the following steps to upgrade to v1.10.0:

    1. Execute the following command and check the zadig.yaml file. If the file contains image information (i.e., tag:a.b.c), it needs to be manually deleted.
    helm get values <Release Name> -n <Zadig Namespace>  > zadig.yaml
    
    1
    1. Execute upgrade command according to installation method.
    • Domain method:
    export NAMESPACE=<Zadig Installation NAMESPACE>
    
    helm repo update
    helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.10.0
    
    1
    2
    3
    4
    • IP + PORT method:
    export NAMESPACE=<Zadig Installation NAMESPACE>
    export PORT=<Any port between 30000-32767, different from initially used port>
    
    helm repo update
    helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
        --set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} \
        --set gloo.gatewayProxies.gatewayProxy.service.type=NodePort --version=1.10.0
    
    1
    2
    3
    4
    5
    6
    7

    Post-Upgrade Considerations

    1. If upgrading from v1.9.0 to v1.10.0 and external clusters were integrated in the Zadig system before upgrade, after upgrading to v1.10.0, you need to disconnect the external cluster connection and re-integrate it, otherwise the functionality of using that cluster for builds will be abnormal. For cluster integration, refer to: Cluster Management.
    2. If build cache was enabled in v1.9.0, you need to explicitly configure the use of Object Storage or Cluster Storage for the cluster where builds are located in Cluster Management. For build cache configuration, refer to: Cache Resource Configuration.
    3. If using a custom account system, after upgrade you need to rebuild and deploy dex according to the documentation.

    ← v1.11.0 Release Notesv1.9.0 Release Notes→

    资源
    教程
    论坛
    博客
    公司
    关于
    客户故事
    加入我们
    联系我们
    微信扫一扫
    hello@koderover.com

    © 2026 筑栈(上海)信息技术有限公司 沪 ICP 备 19000177 号 - 1

    •  跟随系统
    •  浅色模式
    •  深色模式
    •  阅读模式